2013-08-09 - 7003.900 - Spec - SAP AFS Upgrade #SDUpgrade #US

SPECIFICATIONS

7003.900-Spec-SAP AFS Upgrade

Purpose

Upgrade SAP AFS ECC 6.0 to EHP 5 (ECC 6.5) along with all associated support packs.

Admin Info

Purpose
 SAP AFS upgrade to ECC 6.5
Requested By
 Daniel Brennan
Spec Created By
 Surya Basa
Spec Created Date
 08/23/2013
Spec QA by
 Surya Basa
Objects
 RV60AFZC
RV60AFZZ
RV61AFZA
RV63A902
V_T682
V_T685
/AFS/REGISTRY
Document Status
 Resolved

References

Prior Tickets

None

Documents

Upgrade OSS Notes.xlsxNEP_Customized_objects.xlsxSandbox SPDD_SPAU.xlsx


Functional Requirement

Provide Consulting and E2E functional testing support in upgrading the current system SAP AFS ECC 6.0 to SAP AFS ECC 6.0 EHP 5.


Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

1. Upgraded SAP GUI to version 710 patch level 22 to be consistent with the requirements of ECC 6.5
2. Classified and checked the customized objects under T-Codes, Programs and Functional Modules in sandbox environment ECC 6.5.
3. Checked the SD relevant OSS notes in sandbox enviroment in comparision to the existing OSS notes in NEP environmnet.
4. Analysed the impact of new fields on the existing functionality in VBAK, VBAP, LIKP, LIPS and VBRK tables provided with the Enhancement Pack.
5. Analysed OSS notes applicability to the current package SAPK60504INP3A.
6. Analysed SPDD & SPAU entries and provided recommendations if the new code changes could negatively impact the current business functionality.
7. Delta transports were recreated in the new system as per the requirements specified by NEC.
8. Transport issue was resolved in co-ordination with NEC.
9. Recreated transports for the user exits having custom code. The following are the user exits-

10. Created new access sequence ZAST by copying standard VAST access for maintaining VAS condition records. The upgrade has overwritten the custom tables assigned to the standard VAS access sequence.
11. Analysed V.25 report issue in 6.5 and provided feedback to NEC. The issue was caused by additional code in the standard report that also required to maintain a new variable in the table /AFS/REGISTRY.



Test Plan

[List test scenarios/cases to be executed here]

Please refer to the attached spreadsheet for the test details-

Unit Tests NECNED.xls

Solution Details

[Provide complete technical details for configuration or programming here]

Issues

1. JS - MSO Sold-to entry deleted -
JS Partner Function.jpg
This entry was deleted as part of package installation. Currently JM partner function is being used to check for the Ship-to entry to the corresponding Sold-to. However, this entry was added again added as part of the standard upgraded version ECC 6.5 thereby causing an issue in SO creation; the system checks the entry for the ship-to against JS partner function in the customer master data for a given sold-to.

Error Message while creating SO-
Ship-to error.jpg
JS Partner Function Updation Details-
JS Partner Func.-Req Detail.png

JS Partner Function table entry deleted-
JS Part Fucn.-Table Entry.png

2. VAST access sequence had only the standard condition tables assigned as a result of up-gradation.
VAST.png

A new access sequence ZAST was created and the custom condition tables were assigned. The VAS condition type VAST was assigned with the access sequence ZAST.
ZAST.png
VAST.jpg

3. Retrieved the transports having the custom code in ECC 6.5 and created transports in the new number range to be imported in the landscape.